From 6be36f82776914c2a429eab87e4257bbd153bb79 Mon Sep 17 00:00:00 2001 From: "kaf24@scramble.cl.cam.ac.uk" Date: Sat, 24 Jan 2004 01:13:55 +0000 Subject: [PATCH] bitkeeper revision 1.691 (4011c6d3g_Q_DeG3-esCCO1ROch6Rw) XenoUtil.py, VBD-HOWTO.txt: Fix location of xen vbd dataase file. --- docs/VBD-HOWTO.txt | 4 ++-- tools/xc/py/XenoUtil.py | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/VBD-HOWTO.txt b/docs/VBD-HOWTO.txt index 6a276a83b5..9a13404a0a 100644 --- a/docs/VBD-HOWTO.txt +++ b/docs/VBD-HOWTO.txt @@ -86,7 +86,7 @@ Virtual Disk Management The VD management code runs entirely in userspace. The code is written in Python and can therefore be accessed from custom scripts, as well as from the convenience scripts provided. The underlying VD database is a SQLite database -in /var/spool/xen_vdisks.sqlite. +in /var/lib/xen_vdisks.sqlite. The scripts provided are as follows: @@ -131,7 +131,7 @@ More detail: When you use vd_format.py to add a device to the free space pool, the device is logically split up into extents. These extents are recorded in the Virtual -Disk Management database in /var/spool/xen_vdisks.sqlite. +Disk Management database in /var/lib/xen_vdisks.sqlite. When you use vd_create.py to add create a virtual disk, some of the extents in the free space pool are reallocated for that virtual disk and a record for that diff --git a/tools/xc/py/XenoUtil.py b/tools/xc/py/XenoUtil.py index d038e5d204..ee4dd79edc 100644 --- a/tools/xc/py/XenoUtil.py +++ b/tools/xc/py/XenoUtil.py @@ -3,9 +3,9 @@ import string, re, os, sys ##### Module variables """Location of the Virtual Disk management database. - defaults to /var/spool/xen_vdisks.sqlite + defaults to /var/lib/xen_vdisks.sqlite """ -VD_DB_FILE = "/var/spool/xen_vdisks.sqlite" +VD_DB_FILE = "/var/lib/xen_vdisks.sqlite" """VBD expertise level - determines the strictness of the sanity checking. This mode determines the level of complaints when disk sharing occurs -- 2.30.2